Rename CLUSTER env var to CLUSTER_NAME for consistency#4656
Rename CLUSTER env var to CLUSTER_NAME for consistency#4656tuxerrante wants to merge 2 commits intomasterfrom
Conversation
I actually agree with you, |
Yes, i was just about to suggest the same :) I'd prefer to commit to |
430c035 to
1b978bb
Compare
1253959 to
656131f
Compare
CLUSTER_NAME is more descriptive than the bare CLUSTER. This renames the environment variable everywhere: Go code, Makefile, shell scripts, CI pipeline, docker-compose, and documentation.
656131f to
3da45c3
Compare
- Remove unnecessary CLUSTER_NAME env var from operator run command in guardrails README (cmd/aro operator doesn't read it) - Remove stale TODO about billing pipelines (no billing pipelines exist) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
rh-returners
left a comment
There was a problem hiding this comment.
This really makes sense to do , since we need to start working on consistency!
lgtm!
|
This change will break E2E in production which sets cluster name to CLUSTER. We first need to merge a PR there to set both variable in order to avoid E2E "downtime". |
Summary
CLUSTERtoCLUSTER_NAMEinenv.example,hack/setup_resources.sh, and all references I could findTest plan
go build ./...passesgo test ./...passes